A few improvements and fixes have been made to make writing ASLM clients from CodeWarrior easier. You still cannot build ASLM shared libraries from CodeWarrior. To build ASLM clients from CodeWarrior, it is necessary for 68k clients to enable the 4 byte ints and MPW C calling conventions options from the 68K Processor preferences panel. 68K clients should link with the libraries in the THINKLibraries folder and PPC clients should link with the libraries in the MrCLibraries folder.
FlushCache Link Error Fixed
-------------------------
The FlushCache routine, which was accidently ommited from LibraryManagerClient.o, has been added so you won't get link errors any more.
Inspector Example Builds from CodeWarrior
---------------------------------------
A couple of minor changes have been made to the Inspector example so the application will now build under CodeWarrior. To get the Inspector application to build you will need to do the following:
•Create a standard PPC or 68k C++ project.
•Add the ASLM CInterfaces folder as an Access Path and enable the 'Treat #include <…> as #include "…"' option.
•For 68k, from the 68K Processor preferences panel, enable 4 byte ints and MPW C calling conventions.
•Add InspectorMain.cp to the project.
•For 68k, add LibraryManagerClient.o from the THINKLibraries folder.
•For PPC, add LibraryManagerPPC.o from the MrCLibraries folder.
•Add InspectorLibrary.cl.o to the project. Note that you will first need to build the InspectorLibrary from MPW in order to create this file. (You can't build ASLM shared libraries from CodeWarrior).
•Add the Inspector resources to the project. You will need to create an Inspector.RSRC file first. The easiest way to do this is to first build the Inspector or InspectorPPC application from MPW. Then open up the application from ResEdit and delete any 'CODE' and 'cfrg' resources, save the file as Inspector.RSRC, and add it to the project.
LibraryManager.h Supports SingleObject for CodeWarrior
LibraryManager.h has been changed to recognize the fact the CodeWarrior supports SingleObject. Clients developed in CodeWarrior will now generate vtable compatible references to any ASLM class that inherits from TDyamic or uses the SINGLEOBJECT macro.
Improved CodeWarrior Mangled Name Support
----------------------------------------
The LibraryBuilder tool has changed so it will now generate both MPW and CodeWarrior compatible mangled names. The CodeWarrior compatible mangled names will be generated automatically. You don't need to specify any options. This will help get ride of most of the link errors you get when trying to use a C++ class exported from an ASLM shared library.
Note that the LibraryBuilder tool will not generate proper CodeWarrior mangled names for all C++ functions. MrC, SCpp, and CFront all use the letter T in a mangled name to represent a parameter whose type is the same as the previous parameter. CodeWarrior does not use this shorthand notation and LibraryBuilder does not properly convert these names. For example:
void Foo(TRect*, void*, TRect*);
would be mangled as
void Foo__FP5TRectPvT2
Foo__F is for the function name, P5TRect is a pointer to a TRect, Pv is a pointer to a void, and T2 specifies that the parameter is the same as the first one - a pointer to a TRect. T2 is used because it is shorter then repeating P5TRect.
If you have a MrC, SCpp, or CFront mangled name that is using the letter T, then CodeWarrior clients will need to write glue code to use if. Using the Foo() example above, the glue would be as follows:
